home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
8bitfiles.net/archives
/
archives.tar
/
archives
/
compuserve-file-archive
/
23 Geos Applications
/
GEOOBV.THD
< prev
next >
Wrap
Text File
|
2019-04-13
|
8KB
|
210 lines
#: 17398 S13/The GEOS Connection
27-Dec-88 19:11:21
Sb: #GEOS 2.0 Observations
Fm: Ed Flinn/Sysop 76703,4032
To: All
I've noticed a few oddities in GEOS 64 2.0, and thought I'd point them out
for comment.
First, in geoPaint, it seems the value of the color on/off switch has been
reversed. geoPaints that are color on to any other geoPaint will be color off
to the 'Paint in 2.0, and vice versa. Wierd!
Second, this may be documented somewhere, as I haven't read the whole
manual. By carefully positioning a file when you move it to a page, you can
place it at a position other than the first empty slot on the page. It's
tricky, if you're off by just a little, it'll go to the first empty slot, but
it can be done, and it didn't used to be possible.
Related, and documented, it's possible now to switch the positions of two
files on a single page by picking one up and dropping it on the other.
Selecting an input driver from a disk with more than one on it will also swap
the positions so that the one you select will be first on the disk. Haven't
experimented enough to determine if that's only true for boot disks. NOTE:
This means that selecting an input driver is now an output function to the
disk.
Lastly, and probably only of interest to fanatical 1581 owners, GEOS appears
to only support 18 directory pages. It is possible to have disks with more
pages, but there is no way to access pages above 19, or files on them, and any
files on those pages do not count towards the displayed number of files, or
storage used. The only time I have run into this is on a 1581 being used as a
font library, where fonts are small enough that more than 144 can be fit on a
1581. 144 files = 18 full pages = maximum capacity of a 1541. Don't know
about 1571, don't own one. 1581 can physically support, what, 37 pages or 296
files.
Any comments, agreements, or rebuttals will be welcome <grin>
#: 17414 S13/The GEOS Connection
28-Dec-88 14:31:36
Sb: #17398-#GEOS 2.0 Observations
Fm: Anthony Marsh 72127,2301
To: Ed Flinn/Sysop 76703,4032 (X)
Only thing I would be careful about is to not move anything around on the boot
disk. The Trojan horse is still there. I'd rather select my printer later
anyway. And of course it can kill your VORPALized copy anyway if you're not
careful. Is it time for me to upload VORPAL AID here yet? Tony
#: 17423 S13/The GEOS Connection
28-Dec-88 18:28:36
Sb: #17414-GEOS 2.0 Observations
Fm: Ed Flinn/Sysop 76703,4032
To: Anthony Marsh 72127,2301
Anthony,
Certainly it's a very good practice to keep a write-protect tab on any GEOS
boot disk, original or copy. The trojan horse they built into the desktop is,
as you say, still there, and has been reported to occaisionally trash an
original, unhacked boot disk.
I don't think we can have any copy utilities here designed to break
protection. Even though they can legitimately be used by those who license
software to make backups that they are entitled to, per the current copyright
statutes, it's against CIS policy to allow these programs in the forum
libraries. Thanks for thinking of us, tho.
If I'm mistaken here, and Vorpal is *not* designed to break protection, let
me know.
#: 17447 S13/The GEOS Connection
29-Dec-88 14:43:42
Sb: #17414-#GEOS 2.0 Observations
Fm: Marte Brengle 76703,4242
To: Anthony Marsh 72127,2301
I found that you can, to a certain extent, move stuff around on the boot disk.
I ran an "upgrade" on a SuperKit copy of V1.2, for example, and managed to keep
my boot files from being eaten by being *very* careful what I moved, and where.
But once it was all done, the write protect tab went on, never to be removed
again. I don't want all that work eaten up because someone's Trojan Horse
program *thinks* I have a pirate copy.
--M--
#: 17456 S13/The GEOS Connection
29-Dec-88 16:23:35
Sb: #17447-GEOS 2.0 Observations
Fm: Ed Flinn/Sysop 76703,4032
To: Marte Brengle 76703,4242 (X)
Marte,
That's one of the most insidious things about the GEOS Trojan. There is a
random routine in it, designed, I guess, to keep you from realizing that you
weren't experiencing some mysterious bug, but an intentional "feature" of the
software.
#: 17498 S13/The GEOS Connection
31-Dec-88 12:20:24
Sb: #17398-#GEOS 2.0 Observations
Fm: Tweeze 72401,1677
To: Ed Flinn/Sysop 76703,4032 (X)
Pardon me for jumping into the middle of a string but this seems like a good
place for this question. I have Geos 2.0 and am having problems using it with a
1581 and 1541 drive. I am not able to open a datafile for ANY of my
applications if the data and application are on different drives. The manual
states that this is possible for all applications. I have tried every
combination possible with configure but can't get it to work. I would
appreciate any help.
thanx
#: 17499 S13/The GEOS Connection
31-Dec-88 12:33:10
Sb: #17498-GEOS 2.0 Observations
Fm: Ed Flinn/Sysop 76703,4032
To: Tweeze 72401,1677
Tweeze,
Yep, that's a known problem. GEOS only reserves enough memory for one disk
"driver". The disk drivers aren't external files, like input and output
drivers, but are part of the deskTop. If you've got the application on one
drive type, then that type will be held in memory, and the GEOS flag that
controls the number of drives will be set to 1. There are only two ways I know
of to get around this:
1) Keep all data and programs together. While certainly not practical on a
1541, it can be done on a 1581.
2) Buy an REU. When using an REU, GEOS stores all the disk "drivers" for
immediate retrieval. It is then possible to access data on one drive type from
an application resident on another.
If you're running on a 64, then the 1764 is the unit to buy. It has 256k of
memory, and while holding drivers and other odds and ends, can simultaneously
be a RAM 1541, or can "shadow" a real 1541, a form of cacheing.
If you're running in 64 mode on a 128, the 1750 is what you want. It's got
512k, and is fully supported by GEOS 2.0. This is the configuration I normally
run, and it works quite well.
Hope this helps. <ed>
#: 17520 S13/The GEOS Connection
01-Jan-89 18:24:22
Sb: #17499-#GEOS 2.0 Observations
Fm: Tweeze 72401,1677
To: Ed Flinn/Sysop 76703,4032 (X)
I had a feeling that was the case. The wording in the 2.0 manual is a bit vague
about switching drives but never mentions problems mixing drive types in an
application. Maybe the next version will correct this oversight. I am using a
C64 but don't care to purchase an REU just as a cache. As for your 'trojan
horse' I have only seen it wreck the boot files on the first sector of the
directory also. This is simple enough to repair with a sector editor. Just
keep a copy of that sector somewhere else on the disk.
thanx
#: 17521 S13/The GEOS Connection
01-Jan-89 18:29:42
Sb: #17520-GEOS 2.0 Observations
Fm: Ed Flinn/Sysop 76703,4032
To: Tweeze 72401,1677
Tweeze,
I'm not trying to sell you an REU <grin>. It does speed up 1541 operation
considerably. If you've got an '81, you need it much less than those who've
only got '41s. Enjoy!
#: 17638 S13/The GEOS Connection
06-Jan-89 18:00:05
Sb: #17521-GEOS 2.0 Observations
Fm: Tweeze 72401,1677
To: Ed Flinn/Sysop 76703,4032 (X)
I have seen what an REUcan do for geoPAINT. But I don't see any other needs for
it. After having a 1581 for just a short time I am amazed at how much better
it is than my 1541's. My next quest will be for the rummored burst mode chips
for the c-64.
I would say though that overall GEOS version 1.3 was more efficient than 2.0.
#: 17709 S13/The GEOS Connection
11-Jan-89 07:00:49
Sb: #17638-GEOS 2.0 Observations
Fm: Transactor HQ 76703,4243
To: Tweeze 72401,1677
Hi Ed:
Gee, I was really enjoying do all my v2 deskTop work yesterday. All those
keyboard shortcuts.
You might consider JiffyDOS if you're looking for a ROM replacement. The 128
version works in 64 mode and 128 mode.
See our review in Transactor 9:3 (available very soon),
Malcolm